server/src/main/java/com/cloud/vm/UserVmManagerImpl.java:5803

• Initializing params as an empty HashMap changes behavior: createParameterInParameterMap only copies parameterMap (i.e., additionalParams) into params when params == null. With this change, when vm.isUpdateParameters() is true, params will end up containing only the explicitly added entries (e.g., VmPassword), and will no longer include other additionalParams such as UEFI boot options (UefiFlag/BootType/BootMode) or ConsiderLastHost, which are expected downstream (e.g., logged/used during start). Consider initializing params as a copy of additionalParams (or adjusting createParameterInParameterMap to always merge parameterMap) so all start parameters are preserved while still guaranteeing params is non-null.

        // Set parameters
        Map<VirtualMachineProfile.Param, Object> params = new HashMap<>();
        if (vm.isUpdateParameters()) {
            _vmDao.loadDetails(vm);

            String password = getCurrentVmPasswordOrDefineNewPassword(String.valueOf(additionalParams.getOrDefault(VirtualMachineProfile.Param.VmPassword, "")), vm, template);

server/src/main/java/com/cloud/vm/UserVmManagerImpl.java:5803

• This change alters how the start parameter map is built; please add/adjust a unit test to assert the returned params is non-null and still includes entries from additionalParams (e.g., UEFI/boot mode params or ConsiderLastHost) when vm.isUpdateParameters() is true, to prevent regressions in the start/deploy flow.

        // Set parameters
        Map<VirtualMachineProfile.Param, Object> params = new HashMap<>();
        if (vm.isUpdateParameters()) {
            _vmDao.loadDetails(vm);

            String password = getCurrentVmPasswordOrDefineNewPassword(String.valueOf(additionalParams.getOrDefault(VirtualMachineProfile.Param.VmPassword, "")), vm, template);